Repository navigation
chore(release): v1.21.0 — module-owned update channel + per-module auto-update - #335
Merged
Merged
Conversation
…to-update Rolls up #334: Tiger_Update_Provider (a module may own how it detects + applies its own updates, via the neutral register() seam — same descriptor + apply contract, so the Module Manager treats it like any other) and per-module auto-update opt-in (the WordPress "Enable auto-updates" toggle; off by default; the daily job applies only opted-in modules). Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_01ASauLLscjqdsNqBNsx2Typ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release PR for v1.21.0. Bumps
Tiger_Version::VERSION1.20.1 → 1.21.0 and rolls the CHANGELOG[Unreleased]→[1.21.0].Ships (already merged to main in #334):
Tiger_Update_Provider— a module may own its own update channel (neutral register() seam; same descriptor + apply contract, so every module stays visible/applies uniformly in the Module Manager and core never learns where private bytes come from).On merge + tag
v1.21.0, version-check + release-zip fire. This is what ships the provider seam to boxes so the TigerPanel/TigerBilling self-update clients (TIGER-286) activate.🤖 Generated with Claude Code
https://claude.ai/code/session_01ASauLLscjqdsNqBNsx2Typ